BTech CSE 6th Semester · School of Computer Sciences · UPES Dehradun
The way teams are organized fundamentally changes how software is delivered. DevOps requires breaking down silos and building cross-functional capabilities.
A cross-functional team includes all the skills needed to deliver value from idea to production — development, testing, operations, security, and sometimes product management — working together as one unit.
DevOps teams include diverse roles that work collaboratively. Note that these are often overlapping responsibilities rather than strict job titles.
The most important cultural shift in DevOps is the principle that developers are responsible for the code they write — including its operation in production.
"You build it, you run it" means developers who create a service are also responsible for operating it in production. This eliminates the "throw it over the wall" mentality and creates ownership.
Continuous Integration is the foundation of DevOps. It is the practice of merging code changes frequently and automatically building and testing.
Continuous Integration (CI) is the practice of merging all developers' working copies to a shared mainline multiple times a day. Each merge triggers an automated build and test sequence to verify the integration.
Continuous Delivery ensures that code is always in a deployable state. It extends CI by adding deployment preparation to the pipeline.
Continuous Delivery (CD) is the practice of keeping code in a deployable state at all times. Every change that passes CI is automatically built, tested, and prepared for release to production. Deployment to production requires manual approval.
Continuous Deployment takes CD one step further — removing the manual approval gate. Every change that passes tests is automatically deployed to production.
Continuous Deployment is the practice of automatically deploying every change that passes all tests to production. No human approval is required. The deployment pipeline is fully automated from commit to production.
These three practices are often confused, but they represent different stages of the DevOps pipeline with distinct characteristics.
| Aspect | CI | CD (Delivery) | Continuous Deployment |
|---|---|---|---|
| Primary Focus | Integration and testing | Release preparation | Automated production deployment |
| Automation Level | Build + test automated | Build + test + package automated | Build + test + package + deploy automated |
| Human Intervention | None (after commit) | Manual approval for production | None (fully automated) |
| Deployment Frequency | N/A (not about deployment) | On-demand, when approved | Every passing commit |
| Risk Profile | Low (catches integration issues) | Medium (manual control) | High (requires mature practices) |
| Typical Adopters | Most modern teams | Teams moving toward DevOps | Elite DevOps organizations |
Cross-functional teams and continuous delivery practices are the engine that makes DevOps work in practice.